Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pin LLVM versions in github actions #619

Closed
wants to merge 9 commits into from

Conversation

hazelweakly
Copy link
Contributor

This should prevent our builds from failing if LLVM changes underneath as previously we were relying on the first LLVM to be found on the path, which can change without warning.

@kquick
Copy link
Member

kquick commented Jan 28, 2021

With the merge of 624 this is less of an issue now that support for LLVM 11 has been merged in. The remaining failure is a legitimate behavior change in LLVM 11 that I should be able to address in #618.

@hazelweakly
Copy link
Contributor Author

Good to know! It still seems like a good idea to make sure that we know what version of clang we're using. The fact that it worked for so long is a matter of luck more than anything else, and I'd prefer to save my luck for other things :)

@kquick
Copy link
Member

kquick commented Jan 30, 2021

In 618, the clang version is detected and reported as part of the test output.

@robdockins
Copy link
Contributor

I think this is superseded by #753. Feel free to reopen if I'm mistaken.

@robdockins robdockins closed this Jun 3, 2021
@travitch travitch deleted the fix-actions-llvm-version branch August 5, 2022 17:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants